Multicast wakeup in wireless networks

ABSTRACT

The disclosure describes systems and methods for updating multicast wakeup schedules in devices in a mesh network such as a neighborhood area network (NAN) multicast service group (NMSG). The systems and methods enable meshed devices to send and receive routing control messages amongst themselves in accordance with a centralized update protocol, a distributed update protocol, or a hybrid update protocol which is a combination of the centralized and distributed update protocols.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Non-Provisional applicationSer. No. 16/537,235, filed Aug. 9, 2019, which is a continuation of U.S.Non-Provisional application Ser. No. 15/394,428, filed on Dec. 29, 2016,now U.S. Pat. No. 10,383,057, issued on Aug. 13, 2019, which claims thebenefit of U.S. Provisional Application No. 62/378,003, filed on Aug.22, 2016, the disclosures of which are incorporated herein by referenceas if set forth in full.

TECHNICAL FIELD

This disclosure generally relates to systems and methods for wirelesscommunications and, more particularly, systems and methods forscheduling wireless communications.

BACKGROUND

Neighbor Awareness Networks (NANs) such as Wi-Fi Aware represent a powerefficient, scalable, peer-to-peer technology for wireless networking.NAN enables various devices to discover peer devices and/or services intheir proximity and setup data paths with the peer devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a wireless network environment in accordance with exampleembodiments of the disclosure.

FIG. 2 shows a centralized method of multicast wakeup scheduling inwireless mesh networks in accordance with example embodiments of thedisclosure.

FIG. 3 shows a distributed method of multicast wakeup scheduling inwireless mesh networks in accordance with example embodiments of thedisclosure.

FIG. 4 shows a flow diagram from the perspective of a user device,acting as a schedule owner, in methods of multicast wakeup scheduling inwireless mesh networks in accordance with example embodiments of thedisclosure.

FIG. 5 shows a flow diagram from the perspective of a user device,receiving a master multicast wakeup schedule from a schedule owner, in acentralized method of multicast wakeup scheduling in wireless meshnetworks in accordance with example embodiments of the disclosure

FIG. 6 shows a flow diagram from the perspective of a user device,receiving a proposed local multicast wakeup schedule from a scheduleowner, in a distributed method of multicast wakeup scheduling inwireless mesh networks in accordance with example embodiments of thedisclosure.

FIG. 7 illustrates a functional diagram of an example communicationstation suitable for use as a user device in accordance with exampleembodiments of the disclosure.

FIG. 8 shows a block diagram of an example machine upon which any of oneor more techniques (e.g., methods) may be performed in accordance withembodiments of the disclosure.

DETAILED DESCRIPTION

Example embodiments described herein provide certain systems, methods,and devices, for multicast wakeup scheduling in NANs, such as Wi-FiAware.

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

In various embodiments of the disclosure, the word “device” can be usedinterchangeably with the word “node.” For example, a node can also bereferred to as a device and vice-versa.

Neighbor Awareness Networks (NAN's), such as Wi-Fi Aware, can be used sothat devices discover peer devices and/or services in their proximityand setup data paths with one or more peer devices. Mesh devices in aNAN can establish multicast wakeup schedules for use in communicatingwith one another. The multicast wakeup schedules are governed by a setof schedule parameters such as channels and/or timeslots. Multicastwakeup schedules may need to be updated by a mesh device for a varietyof reasons such as power saving, interference avoidance, or frequencyrequirement for routing topology maintenance. Currently, there is nomethod defined for updating multicast wakeup schedules in a many-to-manyNAN multicast service group (NMSG) in Wi-Fi Aware technicalspecifications.

In embodiments, the disclosure provides devices and methods for updatingmulticast wakeup schedules in a mesh network. In embodiments, thedisclosure describes devices and methods for updating multicast wakeupschedules in a many device-to-many device NAN multicast service group(NMSG). In embodiments, a plurality of mesh devices can form a NANmulticast service group, and these devices can send mesh controlmessages to each other and receive mesh control messages from each otherthat can be used to update multicast wakeup schedules. In embodiments,the disclosure introduces methods for updating multicast wakeupschedules that allow a NAN/mesh node to update its multicast wakeupschedule so that its neighbor nodes are able to receive a routingcontrol message for routing table setup and maintenance. In embodiments,the disclosure can generally be used to update multicast wakeupschedules in a NMSG, and can specifically be used for routing protocolmessage exchange in a mesh network. In embodiments, methods of thepresent disclosure are less complex than other existing proposals forupdating multicast wakeup schedules in a NSMG.

In embodiments, devices and methods are provided that allow a meshdevice in a NAN to update multicast wakeup schedules (e.g. updaterouting control information) so that the mesh device can receivemessages from other devices in the mesh network and/or send messages toother devices in the mesh network. For example, one or more mesh devicesin the NMSG can send multicast Destination Oriented Directed AcyclicGraph (DODAG) Information Object (DIO) in routing protocol for low power(RPL) to one or more other mesh devices in the NMSG, or receive the samefrom one or more other mesh devices in the NMSG. In another example, oneor more mesh devices in the NMSG can send a routing control message,such as a routing control message for routing table setup, maintenance,and repairing, to one or more other mesh devices in the NMSG, or receivethe same from one or more other mesh devices in the NMSG.

In embodiments, a mesh networked device's multicast wakeup schedule canbe updated in accordance with one of three different methods describedherein. In embodiments, multicast wakeup schedules can be updated inaccordance with a centralized method, a distributed method, or a hybridmethod which is a combination of both the centralized and distributedmethods.

In a centralized method, only a schedule owner defines and updates amaster multicast wakeup schedule for all devices in the NMSG. Theschedule owner in a centralized method can be, for example, a root node,a founding device, a central mesh node, or a network coordinator, andthe other devices in the NMSG can be relay nodes, leaf nodes, or acombination thereof. In the centralized method, the relay nodes and theleaf nodes all follow the updated master multicast wakeup scheduledetermined and/or sent (e.g., advertised) by the schedule owner. In thecentralized method, for example, the schedule owner can determine and/orsend an updated master multicast wakeup schedule to its neighboringnodes (e.g., relay nodes and/or leaf nodes), the neighboring nodes canthen send the updated master multicast wakeup schedule to theirneighboring nodes, and this process can be repeated until all nodes inthe NMSG have received the updated master multicast wakeup schedule.

In a distributed method, a schedule owner defines and updates a localmulticast wakeup schedule for use in communicating with neighboringdevices in the NMSG. The schedule owner in a distributed method can be,for example, any mesh router in the network (e.g., a root node, afounding device, a network coordinator, or a relay node). In embodimentsof a distributed method, any node in the mesh network can be a source ofmulticast (e.g., a schedule owner), any node can have its own localmulticast wakeup schedule for use in communicating with its neighboringnodes, any node can update its own local multicast wakeup schedule, anynode can send mesh control messages having control information for itsown local multicast wakeup schedule to neighboring nodes, any node canreceive a multicast wakeup schedule from a parent node, any node canreceive mesh control messages having control information for a parentnode's local multicast wakeup schedule, and any node can update itsinternal multicast wakeup schedule so that the node can receivecommunications from a parent node according to the parent node's localmulticast wakeup schedule.

In embodiments of a distributed method, the schedule owner can determineand/or send an updated local multicast wakeup schedule to itsneighboring nodes (e.g., relay nodes and/or leaf nodes), the neighboringnodes can accept the updated local multicast wakeup schedule ornegotiate a mutually agreeable local multicast wakeup schedule updatewith the schedule owner, and the schedule owner and its neighboringnodes can communicate with each other according to the updated localmulticast wakeup schedule. Each neighboring node can also act as aschedule owner with respect to its own neighboring nodes, and arrangeupdated local multicast wakeup schedules with its own neighboring nodesbased, in part, on its local multicast wakeup schedules with otherdevices (e.g. its parent nodes/its own neighbor nodes).

In embodiments, the local multicast wakeup schedule of any node can bestored by its neighboring nodes. In embodiments, a mesh node can storeits neighboring nodes' information and corresponding multicast wakeupschedule. In embodiments, multicast wakeup schedule information may beadded to a table that represents the neighboring nodes.

In a hybrid method, the multicast wakeup schedule of mesh networkeddevices can be updated by a combination of both a centralized method anda distributed method operating in tandem or sequentially. For example,in embodiments, the centralized method can be used to update a mastermulticast wakeup schedule for all devices in the NMSG, which can be usedin the event that a mesh network device loses connectivity with a parentor neighbor node, and the distributed method can be used to update localmulticast wakeup schedules between neighboring nodes, which can be usedfor communications between the neighboring nodes.

FIG. 1 illustrates an example wireless network environment according toexample embodiments of the present disclosure. Wireless network 100 mayinclude one or more user devices 120 and/or one or more access point(s)(AP) 102, which may communicate in accordance with technical standardsthat support NAN protocols, such as IEEE 802.11 communication standards,or generally any system that supports NAN protocols. The device(s) 120may be mobile devices that are non-stationary and do not have fixedlocations.

The user device(s) 120 (e.g., 124, 126, or 128) may include any suitableprocessor-driven user device including, but not limited to, a desktopuser device, a laptop user device, a server, a router, a switch, anaccess point, a smartphone, a tablet, wearable wireless device (e.g.,bracelet, watch, glasses, ring, etc.) and so forth. In some embodiments,the user devices 120 and AP 102 may include one or more computer systemssimilar to that of the functional diagram of FIG. 7 and/or the examplemachine/system of FIG. 8, to be discussed further.

Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP102 may be configured to communicate with each other (e.g. AP to AP, APto user device, user device to user device, etc.) and any othercomponent of the wireless network 100 via one or more communicationsnetworks 130 and/or 135, wirelessly or wired.

Any of the communications networks 130 and/or 135 may include, but notare limited to, any one of a combination of different types of suitablecommunications networks such as, for example, broadcasting networks,cable networks, public networks (e.g., the Internet), private networks,wireless networks, cellular networks, or any other suitable privateand/or public networks. Further, any of the communications networks 130and/or 135 may have any suitable communication range associatedtherewith and may include, for example, global networks (e.g., theInternet), metropolitan area networks (MANs), wide area networks (WANs),local area networks (LANs), personal area networks (PANs), neighborawareness networks (NANs), mesh networks, multi-hop networks, D2Dnetworks, P2P networks, Wi-Fi Aware networks, Wi-Fi networks, BLEnetworks, and NFC networks. In addition, any of the communicationsnetworks 130 and/or 135 may include any type of medium over whichnetwork traffic may be carried including, but not limited to, coaxialcable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC)medium, microwave terrestrial transceivers, radio frequencycommunication mediums, white space communication mediums, ultra-highfrequency communication mediums, satellite communication mediums, or anycombination thereof.

Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP102 may include one or more communications antennas. Communicationsantennas may be any suitable type of antenna corresponding to thecommunications protocols used by the user device(s) 120 (e.g., userdevices 124, 124 and 128), and AP 102. Some non-limiting examples ofsuitable communications antennas include Wi-Fi antennas, Institute ofElectrical and Electronics Engineers (IEEE) 802.11 family of standardscompatible antennas, directional antennas, non-directional antennas,dipole antennas, folded dipole antennas, patch antennas, multiple-inputmultiple-output (MIMO) antennas, or the like. The communications antennamay be communicatively coupled to a radio component to transmit and/orreceive signals, such as communications signals to and/or from the userdevices 120.

Any of the user devices 120 (e.g., user devices 124, 126, 128), and AP102 may include any suitable radio and/or transceiver for transmittingand/or receiving radio frequency (RF) signals in the bandwidth and/orchannels corresponding to the communications protocols utilized by anyof the user device(s) 120 and AP 102 to communicate with each other(e.g. AP to AP, AP to user device, user device to user device, etc.).The radio components may include hardware and/or software to modulateand/or demodulate communications signals according to pre-establishedtransmission protocols. The radio components may further have hardwareand/or software instructions to communicate via one or more Wi-Fi and/orWi-Fi direct protocols, as standardized by the Institute of Electricaland Electronics Engineers (IEEE) 802.11 standards. In certain exampleembodiments, the radio component, in cooperation with the communicationsantennas, may be configured to communicate via 2.4 GHz channels (e.g.802.11b, 802.11g, 802.11n), 5 GHz channels (e.g. 802.11n, 802.11ac), or60 GHZ channels (e.g. 802.11ad). In some embodiments, non-Wi-Fiprotocols may be used for communications between devices, such asBluetooth, dedicated short-range communication (DSRC), Ultra-HighFrequency (UHF) (e.g. IEEE 802.11af, IEEE 802.22), white band frequency(e.g., white spaces), or other packetized radio communications. Theradio component may include any known receiver and baseband suitable forcommunicating via the communications protocols. The radio component mayfurther include a low noise amplifier (LNA), additional signalamplifiers, an analog-to-digital (A/D) converter, one or more buffers,and digital baseband.

FIG. 2 shows a centralized method of master multicast wakeup schedulingin wireless mesh networks in accordance with example embodiments of thedisclosure. A wakeup schedule can include, for example, network resourceallocations such as channel parameters (e.g. time slots/starttime/transmission duration/frequencies/codes) for multicastcommunications and/or other routing control information such asinformation relating to routing table setup, maintenance, and repair.

As shown in FIG. 2, a plurality of mesh devices form a NAN multicastservice group (NMSG) 200, and these devices can send and/or receive meshcontrol messages amongst themselves. The plurality of mesh devices caninclude a schedule owner 202, one or more relay nodes 204, one or moreleaf nodes 206, or a combination thereof. Relay nodes 204 can be anenroller of the NMSG.

According to embodiments of the centralized method, schedule owner 202(e.g. a root node, a founding device, an originator of the NMSG 200, acentral mesh node, or a network coordinator) can determine an updatedmaster multicast wakeup schedule for all devices in the wireless meshnetwork group, including schedule owner 202, any relay nodes 204, andany leaf nodes 206. In embodiments of the centralized method, theschedule owner 202 can define and update a master multicast wakeupschedule for all devices in the NMSG 200, and all devices in the networkfollow the same updated master multicast wakeup schedule.

As shown in FIG. 2, schedule owner 202 determines an updated mastermulticast wakeup schedule and sends (e.g., defines or advertises) theupdated master multicast wakeup schedule to its neighboring nodes. Inthe example embodiment of FIG. 2, relay nodes 204 are the neighboringnodes of schedule owner 202. Relay nodes 204 adopt the updated mastermulticast wakeup schedule they receive from their parent node, which isschedule owner 202 in the example embodiment of FIG. 2. In someembodiments, relay nodes may receive updated master multicast wakeupschedule from other relay nodes. Relay nodes 204 can also send theupdated master multicast wakeup schedule to their neighboring nodes. Inthe example embodiment of FIG. 2, leaf nodes 206 are the neighboringnodes to relay nodes 204. Leaf nodes 206 adopt the updated mastermulticast wakeup schedule they receive from their parent nodes, whichare relay nodes 204 in the example embodiment of FIG. 2. Schedule owner202, relay nodes 204, and leaf nodes 206 can use the updated mastermulticast wakeup schedule to communicate with each other. For example,when a relay or leaf node in the NAN mesh network group 200 receives anupdated master multicast wakeup schedule, the relay or leaf node canstart to use the updated master multicast wakeup schedule for NANmulticast operation (e.g. start NAN multicast operation at the newlyscheduled start time).

In embodiments, an updated master multicast wakeup schedule can beincluded in a NAN Service Discovery frame 142 transmitted in a discoverywindow. In embodiments, an updated master multicast wakeup schedule canbe included in a NAN schedule update frame as a multicast frame.

The NMSG 200 can have any suitable mesh structure. For example, the NMSG200 can have no relay nodes 204, one layer of relay nodes 204 (as shownin FIG. 2), or multiple layers of relay nodes 204 (e.g. one relay nodeis a neighboring node to another relay node). The schedule owner 202 canhave one or more relay nodes 204, one or more leaf nodes 206, or acombination thereof, as neighboring nodes. Each relay node 204 can haveone or more relay nodes 204, one or more leaf nodes 206, or acombination thereof, as neighboring nodes.

A schedule owner 202 may decide to update a master multicast wakeupschedule in response to a network state change or event, particularlywhere doing so provides an improvement in resource utilization or otherbenefit to the mesh network/mesh network devices. For example, aschedule owner may determine that a network state change has occurred(e.g. devices enrolling in or leaving the NMSG, network interference,power consumption changes by a device in the network, changes tofrequency routing topology in the mesh network, changes in trafficpattern, broken communication links, too many lost/dropped packets, toomany requests to join, poor signal quality, changes in networkconfiguration, suboptimal scheduling and resource utilization, etc.) andupdate a master multicast wakeup schedule to improve resource allocationin the network (e.g. timing/frequency/codes/channels, etc.) or provideanother benefit to the mesh network/mesh network devices (improve devicepower consumption, data transmission reliability in the network, signalstrength etc.).

For example, with reference to FIG. 2, schedule owner 202 may detect anetwork state change such as a route change or new nodes joining thenetwork. Schedule owner 202 can determine an updated master multicastwakeup schedule that enables faster and more efficient networkformation/updates. Schedule owner 202 can send the updated mastermulticast wakeup schedule to its neighboring nodes, relay nodes 204.Relay nodes 204 can receive the updated master multicast wakeup scheduleand send it to their neighboring nodes, leaf nodes 206. Schedule owner202, relay nodes 204, and leaf nodes 206 can use the updated mastermulticast wakeup schedule to communicate with each other. The mastermulticast wakeup schedule can, for example, control all communicationsbetween the various devices (nodes 202, 204, and 206) over the linksshown in FIG. 2,

FIG. 3 shows a distributed method of local multicast wakeup schedulingin wireless mesh networks in accordance with example embodiments of thedisclosure. As shown in FIG. 3, a plurality of mesh devices (e.g. nodes302, 304, and/or 306) form a NAN multicast service group (NMSG) 300, andthese devices can send and receive mesh control messages amongstthemselves. The plurality of mesh devices can include, for example, aroot node, an originator of the NMSG, a central mesh node, a networkcoordinator, one or more relay nodes, one or more leaf nodes, orcombinations thereof. The NAN multicast service group 300 can have anysuitable mesh structure. For example, the NMSG can have one or moredifferent schedule owners (e.g. nodes 302 and 304), each having theirown local multicast wakeup schedule with neighboring nodes.

In embodiments of a distributed method, any node in the NMSG 300 (e.g.nodes 302 or 304), other than a leaf node 306, can be a source ofmulticast (e.g. a schedule owner), any node can have its own localmulticast wakeup schedule for use in communicating with neighboringnodes, any node can update its own local multicast wakeup schedule, anynode can send (e.g., define or advertise) mesh control messages havingcontrol information for its own local multicast wakeup schedule toneighboring nodes, any node can receive multicasts from a parent node,any node can receive mesh control messages having control informationfor a parent node's local multicast wakeup schedule, and any node canupdate its internal multicast wakeup schedule so that the node canreceive communications from a parent node according to the parent node'slocal multicast wakeup schedule. In embodiments of the distributedmethod, any node can have its own local multicast wakeup schedule forcommunicating with neighboring nodes, and any node can define and updateits own local multicast wakeup schedule (e.g. the node acts as aschedule owner).

In embodiments, any node's local multicast wakeup schedule can be storedby its neighbor nodes. In embodiments, any node can store a neighboringnode's information and corresponding local multicast wakeup schedule. Inembodiments, when a mesh node receives an acceptable, updated localmulticast wakeup schedule from a neighboring node in the mesh network,the mesh node can store the local multicast wakeup schedule for thatneighbor node and wake up at the updated local schedule to send andreceive communications to and from that neighbor node.

A schedule owner may decide to update a local multicast wakeup schedulein response to a network state change or event, particularly where doingso provides an improvement in resource utilization or other benefit tothe mesh network/mesh network devices. For example, a schedule owner maydetermine that a network state change has occurred (e.g. devicesenrolling in or leaving the NMSG, network interference, powerconsumption changes by a device in the network, changes to frequencyrouting topology in the mesh network, changes in traffic pattern, brokencommunication links, too many lost/dropped packets, too many requests tojoin, poor signal quality, changes in network configuration, suboptimalscheduling and resource utilization, etc.) and update a local multicastwakeup schedule to improve resource allocation in the network (e.g.timing/frequency/codes/channels, etc.) or provide another benefit to themesh network/mesh network devices (improve device power consumption,data transmission reliability in the network, signal strength etc.).

For example, with reference to FIG. 3, node 302 may detect a networkstate change such as signal interference between it and any of itsneighboring nodes (e.g. nodes 304). Node 302 can determine an updatedlocal multicast wakeup schedule, Schedule A, that reduces the signalinterference from any of its neighboring nodes (e.g. nodes 304) whennode 302 and any of the other neighboring nodes (e.g. nodes 304)communicate. Node 302 can send the updated local multicast wakeupschedule to its neighboring nodes, nodes 304. Nodes 304 can receive theupdated local multicast wakeup schedule, and nodes 302 and 304 cancommunicate with one another in accordance with the updated localmulticast wakeup schedule, Schedule A. Nodes 304 may also detect anetwork state, such as a change in resource utilization based on updatedSchedule A (e.g. Schedule A may cause nodes 304 to have a time/frequencyconflict with their own respective multicast wakeup schedules, SchedulesB and C). Nodes 304 can determine updated local multicast wakeupschedules, Schedules B and C, that eliminate the conflict. Nodes 304 cansend the updated local multicast wakeup schedules to their respectiveneighboring nodes, nodes 306. Nodes 306 can receive the respectiveupdated local multicast wakeup schedules, and nodes 304 and 306 cancommunicate with one another in accordance with their respective updatedlocal multicast wakeup schedules, Schedules B and C.

In embodiments of a distributed method, any node that acts as a scheduleowner (e.g. a source of multicast) can determine and/or send an updatedlocal multicast wakeup schedule to its neighboring nodes (e.g. relaynodes and/or leaf nodes). In embodiments of a distributed method, theneighboring nodes can accept the updated local multicast wakeup scheduleor negotiate a mutually agreeable local multicast wakeup schedule updatewith the schedule owner, and the schedule owner and neighboring nodescan then communicate with each other according to the updated localmulticast wakeup schedule. In embodiments of a distributed method, eachnode can act as a schedule owner with respect to its own neighboringnodes and arrange updated local multicast wakeup schedules with its ownneighboring nodes based, in part, on the multicast wakeup schedules ofother devices (e.g. parent nodes/other neighboring nodes/root nodes). Inembodiments, any node's local multicast wakeup schedule can operate at achannel and/or time pre-determined by another node (e.g. a root node, aparent node) and/or a master multicast wakeup schedule.

In embodiments, an updated local multicast wakeup schedule can beincluded in a NAN Service Discovery frame 142 transmitted in a discoverywindow. In embodiments, an updated local multicast wakeup schedule canbe included in a NAN schedule update frame as a multicast frame.

In the example of FIG. 3, the mesh network includes nodes 302, 304, and306. Node 302 is a schedule owner with respect to its neighboring nodes304, and has a local multicast wakeup schedule defined as Schedule A.Nodes 304, in turn, are schedule owners with respect to theirneighboring nodes 306, and have local multicast wakeup schedules definedas Schedule B and Schedule C, respectively. In embodiments of adistributed method, nodes 302 and 304 communicate with one anotheraccording to Schedule A, whereas Nodes 302 communicate with theirrespective neighboring nodes 306 according to Schedule B and Schedule C,respectively. Nodes 302 and 304 can determine and update their localmulticast wakeup schedules with their respective neighboring nodes,nodes 304 and 306.

In embodiments, a hybrid method of updating multicast wakeup schedulesin wireless mesh networks is provided. The hybrid method can employ acombination of both a centralized method and a distributed methodoperating in tandem or sequentially.

In embodiments of a hybrid method, a centralized method can be used toupdate a master multicast wakeup schedule for all devices in the NMSG.In embodiments, only the schedule owner of the master multicast wakeupschedule (e.g. a root node) can determine and update the mastermulticast wakeup schedule. The master multicast wakeup schedule can beused, for example, by a mesh network device to reestablish connectivityin the event that the mesh network device loses connectivity with itsparent and/or neighboring nodes. The mesh network device can use themaster multicast wakeup schedule for communicating with other devices inthe mesh network, looking for new parent and/or neighboring nodes, andthe like.

In embodiments of a hybrid method, once parent/neighboring nodes areestablished in the mesh network, a node can communicate withparent/neighboring nodes according to a local multicast wakeup schedule.In embodiments, any node in the mesh network can be a source of localmulticast with neighboring nodes, and any node can communicate withparent/neighboring nodes according to a local multicast wakeup scheduleestablished between the node and any parent/neighboring nodes. Inembodiments, the distributed method can be used to update localmulticast wakeup schedules between any node and its parent/neighboringnodes.

In embodiments of a hybrid method, an updated master multicast wakeupschedule and/or an updated local multicast wakeup schedule can beincluded in a NAN Service Discovery frame transmitted in one or morediscovery windows. In embodiments, an updated master multicast wakeupschedule and/or an updated local multicast wakeup schedule can beincluded in a NAN schedule update frame at an original schedule.

In embodiments, any node's local multicast wakeup schedule can operateat a channel and/or time pre-determined by another node (e.g. a rootnode, a parent node) and/or a master multicast wakeup schedule. Inembodiments, the time slots in the master multicast wakeup schedule maybe less frequent than the time slots in the distributed multicast wakeupschedule.

FIG. 4 shows a flow diagram of an illustrative process 400 for updatingmulticast wakeup schedules in wireless mesh networks from theperspective of a user device, acting as a schedule owner, in accordancewith example embodiments of the disclosure. The process 400 can apply toa schedule owner in a centralized method, a distributed method, or ahybrid method for updating multicast wakeup schedules. The user devicecan be any mesh router in the mesh network such as a root node, afounding device, an originator of the NMSG, a central mesh node, anetwork coordinator, a relay node, and the like.

At block 402, a user device can determine that a network state changehas occurred in a NAN multicast service group. A network state changecan be any event, detected or determined by any device, that can prompta schedule owner to update a multicast wakeup schedule in the NMSG.Examples of network state changes can include, for example, devicesenrolling in or leaving the NMSG, network interference, powerconsumption changes by a device in the network, changes to frequencyrouting topology in the mesh network, and the like. The schedule ownercan determine that a network state change has occurred by detecting anetwork state change itself, being informed of a network state change byanother device (e.g. another device in the mesh network), or acombination thereof.

At block 404, a user device can determine an updated multicast wakeupschedule in response to determining that a network state change hasoccurred. A wakeup schedule can include, for example, network resourceallocations such as channel parameters (e.g. time slots/starttime/transmission duration/frequencies/codes) for multicastcommunications and/or other routing control information such asinformation relating to routing table setup, maintenance, and repair. Inembodiments, the schedule owner can determine an updated mastermulticast wakeup schedule, an updated local multicast wakeup schedule,or both, based at least in part on the network state change. A scheduleowner can take into account any properties or parameters of the NANmulticast service group in determining an updated multicast wakeupschedule. For example, in determining an updated multicast wakeupschedule, a schedule owner can take into account existing multicastwakeup schedules (e.g. a master multicast wakeup schedule and localmulticast wakeup schedules with parent nodes and/or neighboring nodes).As another example, a schedule owner can take into account devices thathave enrolled in or left the NMSG, devices that have become neighboringnodes or devices that are no longer neighboring nodes to the scheduleowner, network interference, power consumption changes by a device inthe network, changes to frequency routing topology in the mesh network,and the like.

In a centralized method, the schedule owner can determine an updatedmaster multicast wakeup schedule for all devices in the NMSG withoutnegotiating multicast wakeup schedule parameters with any other devicesin the NMSG.

In a distributed method, the schedule owner can determine an updatedlocal multicast wakeup schedule for use in communicating withneighboring devices. The schedule owner can determine an updated localmulticast wakeup schedule with or without negotiating the updatedschedule with neighboring devices. For example, the schedule owner candetermine an updated local multicast wakeup schedule and forceneighboring devices to follow the updated local multicast wakeupschedule. In another example, the schedule owner can determine anupdated local multicast wakeup schedule in concert with optionalfeedback/input from neighboring devices. In some instances, the scheduleowner can determine an updated local multicast wakeup schedule that isagreeable with neighboring devices at first instance, and therefore theupdated local multicast wakeup schedule does not require negotiationwith the neighboring devices. In other instances, the schedule owner candetermine an updated local multicast wakeup schedule by engaging in aback-and-forth negotiation with neighboring devices wherein the scheduleowner and neighboring devices negotiate the parameters of the localmulticast wakeup schedule so that the local multicast wakeup schedule ismutually agreeable to all devices. The back-and-forth negotiation caninclude each device sending proposals or counter-proposals for anupdated local multicast wakeup schedule.

At block 406, a user device can update its internal multicast wakeupschedule to match that of the updated multicast wakeup scheduledetermined in block 404. The user device can use the updated multicastwakeup schedule to communicate with one or more devices in the meshnetwork.

At block 408, the user device can identify neighboring nodes in the NMSGto which the updated multicast wakeup schedule should be sent.

At block 410, the user device can send the updated multicast wakeupschedule to the neighboring nodes identified in block 608.

FIG. 5 shows a flow diagram of an illustrative process 500 for updatingmaster multicast wakeup schedules in wireless mesh networks from theperspective of a user device, acting as a recipient of an updated mastermulticast wakeup schedule, in accordance with example embodiments of thedisclosure. The process 500 can apply to a user device in a centralizedmethod or a hybrid method for updating multicast wakeup schedules. Theuser device can be a mesh router such as a network coordinator or arelay node, or the user device can be a leaf node.

At block 502, a user device can receive an updated master multicastwakeup schedule from a parent node (e.g. a schedule owner or a relaydevice).

At block 504, a user device can update its internal multicast wakeupschedule to match that of the updated master multicast wakeup schedulereceived in block 502. The user device can use the updated mastermulticast wakeup schedule to communicate with one or more devices in themesh network.

At block 506, a user device determines if there are neighboring nodes towhich to send the updated master multicast wakeup schedule. If the userdevice is a leaf node, then the user device can determine that there areno neighboring nodes to which to send the updated master multicastwakeup schedule. If the user device is a relay node, then the userdevice can determine that there are neighboring nodes to which to sendthe updated master multicast wakeup schedule.

At block 508, the user device has determined that there are noneighboring nodes to which to send the updated master multicast wakeupschedule, and process 500 ends.

At block 510, the user device has determined that there are neighboringnodes to which to send the updated master multicast wakeup schedule. Theuser device can send the updated master multicast wakeup schedule to anyneighboring nodes. As may be indicated in the master multicast wakeupschedule, the user device may implement the new schedule at thedesignate time.

FIG. 6 shows a flow diagram of an illustrative process 600 for updatinglocal multicast wakeup schedules in wireless mesh networks from theperspective of a user device, acting as a recipient of a proposed localmulticast wakeup schedule update, in accordance with example embodimentsof the disclosure. The process 600 can apply to a user device in adistributed method or a hybrid method for updating local multicastwakeup schedules. The user device can be a mesh router such as a networkcoordinator or a relay node, or the user device can be a leaf node.

At block 602, a user device can receive a proposed local multicastwakeup schedule update from a parent node (e.g. a schedule owner).

At block 604, a user device can determine if the proposed localmulticast wakeup schedule update is acceptable. A user device candetermine that a proposed local multicast wakeup schedule update isacceptable or unacceptable for a variety of reasons. A proposed localmulticast wakeup schedule update can be acceptable, for example, whenthe proposed multicast wakeup schedule does not conflict with othermulticast wakeup schedules utilized by the user device and/or theproposed multicast wakeup schedule is an efficient use of networkresources. A proposed local multicast wakeup schedule update can beunacceptable, for example, when the proposed multicast wakeup scheduleconflicts with other multicast wakeup schedules utilized by the userdevice and/or the proposed multicast wakeup schedule is an inefficientuse of network resources.

At block 606, the user device has determined that the proposed localmulticast wakeup schedule update from the parent node is acceptable. Inembodiments, the user device can determine and/or generate a new localmulticast wakeup schedule for itself, based at least in part, on theproposed local multicast wakeup schedule update from the parent node.The user device can determine a new local multicast wakeup scheduletaking into account any properties or parameters of the NAN multicastservice group. For example, in determining a new local multicast wakeupschedule, the user device can take into account existing multicastwakeup schedules (e.g. a master multicast wakeup schedule or a localmulticast wakeup schedule with its parent nodes or neighboring nodes).As another example, a user device can take into account devices thathave become neighboring nodes or devices that are no longer neighboringnodes to the user device, network interference, power consumptionchanges by a device in the network, changes to frequency routingtopology in the mesh network, and the like. The new local multicastwakeup schedule can be determined by engaging in a back-and-forthnegotiation with neighboring devices wherein the user device andneighboring devices negotiate the parameters of the local multicastwakeup schedule so that the local multicast wakeup schedule is mutuallyagreeable to all devices.

At block 608, a user device can update its internal multicast wakeupschedule to match that of the new local multicast wakeup scheduledetermined/generated in block 606. The user device can use the new localmulticast wakeup schedule to communicate with one or more devices in themesh network (e.g. any parent devices and any neighboring devices).

At block 610, a user device determines if there are neighboring nodes towhich to send the new local multicast wakeup schedule. If the userdevice is a leaf node, then the user device can determine that there areno neighboring nodes to which to send the new local multicast wakeupschedule. If the user device is a relay node, then the user device candetermine that there are neighboring nodes to which to send the newlocal multicast wakeup schedule.

At block 612 the user device has determined that there are noneighboring nodes to which to send the new local multicast wakeupschedule, and process 600 ends.

At block 614, the user device has determined that there are neighboringnodes to which to send the new local multicast wakeup schedule. The userdevice can send the new local multicast wakeup schedule to anyneighboring nodes.

At block 616, the user device has determined that the proposed localmulticast wakeup schedule update from the parent node is unacceptable.The user device can then engage in a process for conflict resolution.For example, in view of the proposed local multicast wakeup scheduleupdate from the parent node, the user device can determine whether tostay connected with the parent device or disband the connection with theparent device. The user device can determine to stay connected to ordisconnect from a parent device for a variety of reasons. For example, auser device may determine to remain connected to a parent device if theuser device has not engaged in sufficient back-and-forth negotiationwith a parent device, and the user device may determine to disconnectfrom a parent device if the user device has engaged in sufficientback-and-forth negotiation with a parent device. For example, a userdevice may be configured to require determining and sending a certainnumber of local multicast wakeup schedule counter-proposals to theparent device (e.g. 1, 2, 3, 4, 5, 6, or 7 counter-proposals), and onlyupon sending a certain required number of local multicast wakeupschedule counter-proposals can the user device then decide todiscontinue its connection with the parent device. For illustrativepurposes, a user device may decide to remain connected to a parentdevice if it has sent two or fewer local multicast wakeup schedulecounter-proposals to a parent device, and a user device may decide todisconnect from a parent device if it has sent three or more localmulticast wakeup schedule counter-proposals to a parent device.

At block 618, the user device has determined to disconnect from theparent device, and process 600 ends.

At block 620, the user device has determined to remain connected to theparent device. The user device can engage in a conflict resolutionprocess with the parent device. For example, the user device candetermine a local multicast wakeup schedule counter-proposal to governthe local multicast wakeup schedule between the user device and theparent node. The user device can determine a local multicast wakeupschedule counter-proposal taking into account any properties orparameters of the NAN multicast service group. For example, indetermining a local multicast wakeup schedule counter-proposal, the userdevice can take into account existing or proposed multicast wakeupschedules (e.g. a master multicast wakeup schedule, a proposed localmulticast wakeup schedule from the parent node, and local multicastwakeup schedules with parent/neighboring nodes). As another example, auser device can take into account devices that have become neighboringnodes or devices that are no longer neighboring nodes to the userdevice, network interference, power consumption changes by a device inthe network, changes to frequency routing topology in the mesh network,and the like.

At block 622, the user device can send the local multicast wakeupschedule counter-proposal to the parent node.

At block 624, the user device can determine if its local multicastwakeup schedule counter-proposal to the parent node was accepted by theparent node. The user device can determine that its local multicastwakeup schedule counter-proposal to the parent node was accepted by theparent node if, for example, the user device receives a message from theparent node indicating acceptance (e.g. receipt of an ack or a proposedlocal multicast schedule update from the parent node that is the same asthe local multicast wakeup schedule counter-proposal). If the userdevice determines that the parent node accepted the local multicastwakeup schedule counter-proposal, the user device can proceed to block608.

The user device can determine that its local multicast wakeup schedulecounter- proposal to the parent node was rejected by the parent node if,for example, the user device receives a message from the parent nodeindicating rejection (e.g. receipt of a nack or a proposed localmulticast schedule update from the parent node that is different fromthe local multicast wakeup schedule counter-proposal). If the userdevice determines that the parent node rejected the local multicastwakeup schedule counter-proposal, the user device can proceed to block616.

FIG. 7 shows a functional diagram of an exemplary communication station700 in accordance with some embodiments. In one embodiment, FIG. 7illustrates a functional block diagram of a communication station thatmay be suitable for use as an AP 102 (FIG. 1) or communication stationuser device 120 (FIG. 1) in accordance with some embodiments. Thecommunication station 700 may also be suitable for use as a handhelddevice, mobile device, cellular telephone, smartphone, tablet, netbook,wireless terminal, laptop computer, wearable computer device, femtocell,High Data Rate (HDR) subscriber station, access point, access terminal,or other personal communication system (PCS) device.

The communication station 700 may include communications circuitry 702and a transceiver 710 for transmitting and receiving signals to and fromother communication stations using one or more antennas 701. Thecommunications circuitry 702 may include circuitry that can operate thephysical layer communications and/or medium access control (MAC)communications for controlling access to the wireless medium, and/or anyother communications layers for transmitting and receiving signals. Thecommunication station 700 may also include processing circuitry 706 andmemory 708 arranged to perform the operations described herein. In someembodiments, the communications circuitry 702 and the processingcircuitry 706 may be configured to perform operations detailed in FIGS.1-6.

In accordance with some embodiments, the communications circuitry 702may be arranged to contend for a wireless medium and configure frames orpackets for communicating over the wireless medium. The communicationscircuitry 702 may be arranged to transmit and receive signals. Thecommunications circuitry 702 may also include circuitry formodulation/demodulation, upconversion/downconversion, filtering,amplification, etc. In some embodiments, the processing circuitry 706 ofthe communication station 700 may include one or more processors. Inother embodiments, two or more antennas 701 may be coupled to thecommunications circuitry 702 arranged for sending and receiving signals.The memory 708 may store information for configuring the processingcircuitry 706 to perform operations for configuring and transmittingmessage frames and performing the various operations described herein.The memory 708 may include any type of memory, including non-transitorymemory, for storing information in a form readable by a machine (e.g., acomputer). For example, the memory 708 may include a computer-readablestorage device may, read-only memory (ROM), random-access memory (RAM),magnetic disk storage media, optical storage media, flash-memory devicesand other storage devices and media.

In some embodiments, the communication station 700 may be part of aportable wireless communication device, such as a personal digitalassistant (PDA), a laptop or portable computer with wirelesscommunication capability, a web tablet, a wireless telephone, asmartphone, a wireless headset, a pager, an instant messaging device, adigital camera, an access point, a television, a medical device (e.g., aheart rate monitor, a blood pressure monitor, etc.), a wearable computerdevice, or another device that may receive and/or transmit informationwirelessly.

In some embodiments, the communication station 700 may include one ormore antennas 701. The antennas 701 may include one or more directionalor omnidirectional antennas, including, for example, dipole antennas,monopole antennas, patch antennas, loop antennas, microstrip antennas,or other types of antennas suitable for transmission of RF signals. Insome embodiments, instead of two or more antennas, a single antenna withmultiple apertures may be used. In these embodiments, each aperture maybe considered a separate antenna. In some multiple-input multiple-output(MIMO) embodiments, the antennas may be effectively separated forspatial diversity and the different channel characteristics that mayresult between each of the antennas and the antennas of a transmittingstation.

In some embodiments, the communication station 700 may include one ormore of a keyboard, a display, a non-volatile memory port, multipleantennas, a graphics processor, an application processor, speakers, andother mobile device elements. The display may be an LCD screen includinga touch screen.

Although the communication station 700 is illustrated as having severalseparate functional elements, two or more of the functional elements maybe combined and may be implemented by combinations ofsoftware-configured elements, such as processing elements includingdigital signal processors (DSPs), and/or other hardware elements. Forexample, some elements may include one or more microprocessors, DSPs,field-programmable gate arrays (FPGAs), application specific integratedcircuits (ASICs), radio-frequency integrated circuits (RFICs) andcombinations of various hardware and logic circuitry for performing atleast the functions described herein. In some embodiments, thefunctional elements of the communication station 700 may refer to one ormore processes operating on one or more processing elements.

Certain embodiments may be implemented in one or a combination ofhardware, firmware, and software. Other embodiments may also beimplemented as instructions stored on a computer-readable storagedevice, which may be read and executed by at least one processor toperform the operations described herein. A computer-readable storagedevice may include any non-transitory memory mechanism for storinginformation in a form readable by a machine (e.g., a computer). Forexample, a computer-readable storage device may include read-only memory(ROM), random-access memory (RAM), magnetic disk storage media, opticalstorage media, flash-memory devices, and other storage devices andmedia. In some embodiments, the communication station 700 may includeone or more processors and may be configured with instructions stored ona computer-readable storage device memory.

FIG. 8 illustrates a block diagram of an example of a machine 800 orsystem upon which any one or more of the techniques (e.g.,methodologies) discussed herein may be performed. In other embodiments,the machine 800 may operate as a standalone device or may be connected(e.g., networked) to other machines. In a networked deployment, themachine 800 may operate in the capacity of a server machine, a clientmachine, or both in server-client network environments. In an example,the machine 800 may act as a peer machine in peer-to-peer (P2P) (orother distributed) network environments. The machine 1000 may be apersonal computer (PC), a tablet PC, a set-top box (STB), a personaldigital assistant (PDA), a mobile telephone, wearable computer device, aweb appliance, a network router, switch or bridge, or any machinecapable of executing instructions (sequential or otherwise) that specifyactions to be taken by that machine, such as a base station. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein, such as cloudcomputing, software as a service (SaaS), or other computer clusterconfigurations.

Examples, as described herein, may include or may operate on logic or anumber of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operationswhen operating. A module includes hardware. In an example, the hardwaremay be specifically configured to carry out a specific operation (e.g.,hardwired). In another example, the hardware may include configurableexecution units (e.g., transistors, circuits, etc.) and a computerreadable medium containing instructions where the instructions configurethe execution units to carry out a specific operation when in operation.The configuring may occur under the direction of the executions units ora loading mechanism. Accordingly, the execution units arecommunicatively coupled to the computer-readable medium when the deviceis operating. In this example, the execution units may be a member ofmore than one module. For example, under operation, the execution unitsmay be configured by a first set of instructions to implement a firstmodule at one point in time and reconfigured by a second set ofinstructions to implement a second module at a second point in time.

The machine (e.g., computer system) 800 may include a hardware processor802 (e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 1004 and a static memory 806, some or all of which maycommunicate with each other via an interlink (e.g., bus) 808. Themachine 800 may further include a power management device 832, agraphics display device 810, an alphanumeric input device 812 (e.g., akeyboard), and a user interface (UI) navigation device 814 (e.g., amouse). In an example, the graphics display device 810, alphanumericinput device 812, and UI navigation device 814 may be a touch screendisplay. The machine 800 may additionally include a storage device(i.e., drive unit) 816, a signal generation device 818 (e.g., aspeaker), a wakeup device 819, a network interface device/transceiver820 coupled to antenna(s) 830, and one or more sensors 828, such as aglobal positioning system (GPS) sensor, compass, accelerometer, or othersensor. The machine 800 may include an output controller 834, such as aserial (e.g., universal serial bus (USB), parallel, or other wired orwireless (e.g., infrared (IR), near field communication (NFC), etc.)connection to communicate with or control one or more peripheral devices(e.g., a printer, card reader, etc.)).

The storage device 816 may include a machine readable medium 822 onwhich is stored one or more sets of data structures or instructions 824(e.g., software) embodying or utilized by any one or more of thetechniques or functions described herein. The instructions 824 may alsoreside, completely or at least partially, within the main memory 804,within the static memory 806, or within the hardware processor 802during execution thereof by the machine 800. In an example, one or anycombination of the hardware processor 802, the main memory 804, thestatic memory 806, or the storage device 816 may constitutemachine-readable media.

The wakeup device 819 may be configured to update multicast wakeupschedules in a mesh network such as a NAN. The wakeup device 819 may befurther configured to determine that a network state change has occurredin a mesh network; determine, based at least in part on the networkchange, a first multicast wakeup schedule for use in communicating inthe mesh network; determine one or more neighboring devices in the meshnetwork to send the first multicast wakeup schedule; and cause to sendthe first multicast wakeup schedule to the one or more neighboringdevices. The wakeup device 819 may be further configured to identify afirst multicast wakeup schedule received from a parent device in a meshnetwork; determine a second multicast wakeup schedule that is differentfrom the first multicast wakeup schedule; determine one or moreneighboring devices in the mesh network; and cause to send the secondmulticast wakeup schedule to the one or more neighboring devices. Thewakeup device 819 may be further configured to identify a multicastwakeup schedule received from a parent device in a mesh network; updatean internal multicast wakeup schedule of the wireless device using themulticast wakeup schedule; determine one or more neighboring devices inthe mesh network; and cause to send the multicast wakeup schedule to theone or more neighboring devices.

It is understood that the above are only a subset of what the wakeupdevice 819 may be configured to perform and that other functionsincluded throughout this disclosure may also be performed by the wakeupdevice 819.

While the machine-readable medium 822 is illustrated as a single medium,the term “machine-readable medium” may include a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) configured to store the one or moreinstructions 824.

Various embodiments may be implemented fully or partially in softwareand/or firmware. This software and/or firmware may take the form ofinstructions contained in or on a non-transitory computer-readablestorage medium. Those instructions may then be read and executed by oneor more processors to enable performance of the operations describedherein. The instructions may be in any suitable form, such as but notlimited to source code, compiled code, interpreted code, executablecode, static code, dynamic code, and the like. Such a computer-readablemedium may include any tangible non-transitory medium for storinginformation in a form readable by one or more computers, such as but notlimited to read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; a flash memory, etc.

The term “machine-readable medium” may include any medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine 800 and that cause the machine 800 to perform any one ormore of the techniques of the present disclosure, or that is capable ofstoring, encoding, or carrying data structures used by or associatedwith such instructions. Non-limiting machine-readable medium examplesmay include solid-state memories and optical and magnetic media. In anexample, a massed machine-readable medium includes a machine-readablemedium with a plurality of particles having resting mass. Specificexamples of massed machine-readable media may include non-volatilememory, such as semiconductor memory devices (e.g., ElectricallyProgrammable Read-Only Memory (EPROM), or Electrically ErasableProgrammable Read-Only Memory (EEPROM)) and flash memory devices;magnetic disks, such as internal hard disks and removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 824 may further be transmitted or received over acommunications network 826 using a transmission medium via the networkinterface device/transceiver 820 utilizing any one of a number oftransfer protocols (e.g., frame relay, internet protocol (IP),transmission control protocol (TCP), user datagram protocol (UDP),hypertext transfer protocol (HTTP), etc.). Example communicationsnetworks may include a local area network (LAN), a wide area network(WAN), a packet data network (e.g., the Internet), mobile telephonenetworks (e.g., cellular networks), Plain Old Telephone (POTS) networks,wireless data networks (e.g., Institute of Electrical and ElectronicsEngineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16family of standards known as WiMax®), IEEE 802.15.4 family of standards,and peer-to-peer (P2P) networks, among others. In an example, thenetwork interface device/transceiver 820 may include one or morephysical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or moreantennas to connect to the communications network 826. In an example,the network interface device/transceiver 820 may include a plurality ofantennas to wirelessly communicate using at least one of single-inputmultiple-output (SIMO), multiple-input multiple-output (MIMO), ormultiple-input single-output (MISO) techniques. The term “transmissionmedium” shall be taken to include any intangible medium that is capableof storing, encoding, or carrying instructions for execution by themachine 800 and includes digital or analog communications signals orother intangible media to facilitate communication of such software. Theoperations and processes described and shown above may be carried out orperformed in any suitable order as desired in various implementations.Additionally, in certain implementations, at least a portion of theoperations may be carried out in parallel. Furthermore, in certainimplementations, less than or more than the operations described may beperformed.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any embodiment described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments. The terms “computing device”, “userdevice”, “communication station”, “station”, “handheld device”, “mobiledevice”, “wireless device” and “user equipment” (UE) as used hereinrefers to a wireless communication device such as a cellular telephone,smartphone, tablet, netbook, wireless terminal, laptop computer, afemtocell, High Data Rate (HDR) subscriber station, access point,printer, point of sale device, access terminal, or other personalcommunication system (PCS) device. The device may be either mobile orstationary.

As used within this document, the term “communicate” is intended toinclude transmitting, or receiving, or both transmitting and receiving.This may be particularly useful in claims when describing theorganization of data that is being transmitted by one device andreceived by another, but only the functionality of one of those devicesis required to infringe the claim. Similarly, the bidirectional exchangeof data between two devices (both devices transmit and receive duringthe exchange) may be described as ‘communicating’, when only thefunctionality of one of those devices is being claimed. The term“communicating” as used herein with respect to a wireless communicationsignal includes transmitting the wireless communication signal and/orreceiving the wireless communication signal. For example, a wirelesscommunication unit, which is capable of communicating a wirelesscommunication signal, may include a wireless transmitter to transmit thewireless communication signal to at least one other wirelesscommunication unit, and/or a wireless communication receiver to receivethe wireless communication signal from at least one other wirelesscommunication unit.

The term “access point” (AP) as used herein may be a fixed station. Anaccess point may also be referred to as an access node, a base station,or some other similar terminology known in the art. An access terminalmay also be called a mobile station, user equipment (UE), a wirelesscommunication device, or some other similar terminology known in theart. Embodiments disclosed herein generally pertain to wirelessnetworks. Some embodiments can relate to wireless networks that operatein accordance with one of the IEEE 802.11 standards.

Some embodiments may be used in conjunction with various devices andsystems, for example, a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a handheld device, aPersonal Digital Assistant (PDA) device, a handheld PDA device, anon-board device, an off-board device, a hybrid device, a vehiculardevice, a non-vehicular device, a mobile or portable device, a consumerdevice, a non-mobile or non-portable device, a wireless communicationstation, a wireless communication device, a wireless Access Point (AP),a wired or wireless router, a wired or wireless modem, a video device,an audio device, an audio-video (A/V) device, a wired or wirelessnetwork, a wireless area network, a Wireless Video Area Network (WVAN),a Local Area Network (LAN), a Wireless LAN (WLAN), a Personal AreaNetwork (PAN), a Wireless PAN (WPAN), and the like.

Some embodiments may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, aPersonal Communication Systems (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device, e.g., a Smartphone, aWireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems following one or morewireless communication protocols, for example, Radio Frequency (RF),Infra Red (IR), Frequency-Division Multiplexing (FDM), Orthogonal FDM(OFDM), Time-Division Multiplexing (TDM), Time-Division Multiple Access(TDMA), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS),extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA(WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA,Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®,Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra-Wideband(UWB), Global System for Mobile communication (GSM), 2G, 2.5G, 3G, 3.5G,4G, Fifth Generation (5G) mobile networks, 3GPP, Long Term Evolution(LTE), LTE advanced, Enhanced Data rates for GSM Evolution (EDGE), orthe like. Other embodiments may be used in various other devices,systems, and/or networks.

Certain aspects of the disclosure are described above with reference toblock and flow diagrams of systems, methods, apparatuses, and/orcomputer program products according to various implementations. It willbe understood that one or more blocks of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and the flowdiagrams, respectively, can be implemented by computer-executableprogram instructions Likewise, some blocks of the block diagrams andflow diagrams may not necessarily need to be performed in the orderpresented, or may not necessarily need to be performed at all, accordingto some implementations.

These computer-executable program instructions may be loaded onto aspecial-purpose computer or other particular machine, a processor, orother programmable data processing apparatus to produce a particularmachine, such that the instructions that execute on the computer,processor, or other programmable data processing apparatus create meansfor implementing one or more functions specified in the flow diagramblock or blocks. These computer program instructions may also be storedin a computer-readable storage media or memory that can direct acomputer or other programmable data processing apparatus to function ina particular manner, such that the instructions stored in thecomputer-readable storage media produce an article of manufactureincluding instruction means that implement one or more functionsspecified in the flow diagram block or blocks. As an example, certainimplementations may provide for a computer program product, comprising acomputer-readable storage medium having a computer-readable program codeor program instructions implemented therein, said computer-readableprogram code adapted to be executed to implement one or more functionsspecified in the flow diagram block or blocks. The computer programinstructions may also be loaded onto a computer or other programmabledata processing apparatus to cause a series of operational elements orsteps to be performed on the computer or other programmable apparatus toproduce a computer-implemented process such that the instructions thatexecute on the computer or other programmable apparatus provide elementsor steps for implementing the functions specified in the flow diagramblock or blocks.

Accordingly, blocks of the block diagrams and flow diagrams supportcombinations of means for performing the specified functions,combinations of elements or steps for performing the specified functionsand program instruction means for performing the specified functions. Itwill also be understood that each block of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and flowdiagrams, can be implemented by special-purpose, hardware-based computersystems that perform the specified functions, elements or steps, orcombinations of special-purpose hardware and computer instructions.

Example 1 is a wireless device comprising memory and processingcircuitry configured to: determine that a network state change hasoccurred in a mesh network; determine, based at least in part on thenetwork change, a first multicast wakeup schedule for use incommunicating in the mesh network; determine one or more neighboringdevices in the mesh network to send the first multicast wakeup schedule;and cause to send the first multicast wakeup schedule to the one or moreneighboring devices. In example 2, the device of example 1 canoptionally include the first multicast wakeup schedule being a mastermulticast wakeup schedule. In example 3, the device of any one ofexamples 1-2 can optionally include the first multicast wakeup schedulebeing a local multicast wakeup schedule. In example 4, the device of anyone of examples 1-3 can optionally include the first multicast wakeupschedule being sent to the one or more neighboring devices in a neighborawareness network multicast service group (NMSG) message. In example 5,the device of any one of examples 1-4 can optionally include the firstmulticast wakeup schedule being sent to the one or more neighboringdevices in a neighbor awareness network service discovery frame that issent in a discovery window. In example 6, the device of any one ofexamples 1-5 can optionally include the first multicast wakeup schedulebeing sent to the one or more neighboring devices in a neighborawareness network schedule update frame. In example 7, the device of anyone of examples 1-6 can optionally include the mesh network being aneighborhood area network. In example 8, the device of any one ofexamples 1-7 can optionally include the network state change comprisinga user device enrolling in the mesh network, a user device leaving themesh network, network inference in the mesh network, a power consumptionchange by a user device in the mesh network, or a change in frequencyrouting topology in the mesh network. In example 9, the device of anyone of examples 1-8 can optionally include the first multicast wakeupschedule including a resource allocation for multicast operation. Inexample 10, the device of any one of examples 1-9 can optionally includethe resource allocation including a start time. In example 11, thedevice of any one of examples 1-10 can optionally include the memory andprocessing circuitry being further configured to: identify a secondmulticast wakeup schedule received from a first neighboring device ofthe one or more neighboring devices; determine a third multicast wakeupschedule, based at least in part on the second multicast wakeupschedule, for use in communicating in the mesh network; and cause tosend the third multicast wakeup schedule to the one or more neighboringdevices.

Example 12 is a wireless device comprising memory and processingcircuitry configured to: identify a multicast wakeup schedule receivedfrom a parent device in a mesh network; update an internal multicastschedule of the wireless device using the multicast wakeup schedule;determine one or more neighboring devices in the mesh network; and causeto send the multicast wakeup schedule to the one or more neighboringdevices. In example 13, the device of example 12 can optionally includethe multicast wakeup schedule being a master multicast wakeup schedule.In example 14, the device of any one of examples 12-13 can optionallyinclude the multicast wakeup schedule including a resource allocationfor multicast operation. In example 15, the device of any one ofexamples 12-14 can optionally include the resource allocation includinga start time.

Example 16 is a wireless device comprising memory and processingcircuitry configured to: identify a first multicast wakeup schedulereceived from a parent device in a mesh network; determine a secondmulticast wakeup schedule that is different from the first multicastwakeup schedule; determine one or more neighboring devices in the meshnetwork; and cause to send the second multicast wakeup schedule to theone or more neighboring devices. In example 17, the device of example 16can optionally include the first multicast wakeup schedule and thesecond multicast wakeup schedule allowing complimentary use of networkresources at the wireless device. In example 18, the device of any oneof examples 16-17 can optionally include the second multicast wakeupschedule being based at least in part on the first wakeup schedule. Inexample 19, the device of any one of examples 16-18 can optionallyinclude the memory and processing circuitry are further configured to:determine to send to the parent device a third multicast wakeup schedulethat is different from the first multicast wakeup schedule; determinethe third multicast wakeup schedule based at least in part on the firstmulticast wakeup schedule; cause to send the third multicast wakeupschedule to the parent device; and identify a fourth multicast wakeupschedule received from the parent device, wherein the second multicastwakeup schedule is based at least in part on the fourth multicast wakeupschedule. In example 20, the device of any one of examples 16-19 canoptionally include the first multicast schedule comprising a mastermulticast wakeup schedule and a local multicast wakeup schedule, and thesecond multicast wakeup schedule comprising the master multicast wakeupschedule.

Example 21 is a non-transitory computer-readable medium storingcomputer-executable instructions which, when executed by a processor,cause the processor to perform operations comprising: identifying amulticast wakeup schedule received from a parent device in a meshnetwork; updating an internal multicast schedule of a wireless deviceusing the multicast wakeup schedule; determining one or more neighboringdevices in the mesh network; and causing to send the multicast wakeupschedule to the one or more neighboring devices. In example 22, thecomputer-readable medium of example 21 can optionally include themulticast wakeup schedule being a master multicast wakeup schedule.

Example 23 is a non-transitory computer-readable medium storingcomputer-executable instructions which, when executed by a processor,cause the processor to perform operations comprising: determining that anetwork state change has occurred in a mesh network; determining, basedat least in part on the network change, a first multicast wakeupschedule for use in communicating in the mesh network; determining oneor more neighboring devices in the mesh network to send the firstmulticast wakeup schedule; and causing to send the first multicastwakeup schedule to the one or more neighboring devices. In example 24,the computer-readable medium of example 23 can optionally include thefirst multicast wakeup schedule being a master multicast wakeupschedule. In example 25, the computer-readable medium of any one ofexamples 23-24 can optionally include the first multicast wakeupschedule being a local multicast wakeup schedule. In example 26, thecomputer-readable medium of any one of examples 23-25 can optionallyinclude the first multicast wakeup schedule being sent to the one ormore neighboring devices in a neighbor awareness network multicastservice group (NMSG) message. In example 27, the computer-readablemedium of any one of examples 23-26 can optionally include the firstmulticast wakeup schedule being sent to the one or more neighboringdevices in a neighbor awareness network service discovery frame that issent in a discovery window. In example 28, the computer-readable mediumof any one of examples 23-27 can optionally include the first multicastwakeup schedule being sent to the one or more neighboring devices in aneighbor awareness network schedule update frame. In example 29, thecomputer-readable medium of any one of examples 23-28 can optionallyinclude the mesh network being a neighborhood area network. In example30, the computer-readable medium of any one of examples 23-29 canoptionally include the network state change comprising a user deviceenrolling in the mesh network, a user device leaving the mesh network,network inference in the mesh network, a power consumption change by auser device in the mesh network, or a change in frequency routingtopology in the mesh network. In example 31, the computer-readablemedium of any one of examples 23-30 can optionally include the firstmulticast wakeup schedule includes a resource allocation for multicastoperation. In example 32, the computer-readable medium of any one ofexamples 23-31 can optionally include the resource allocation includinga start time. In example 33, the computer-readable medium of any one ofexamples 23-32 can optionally include the operations further comprising:identifying a second multicast wakeup schedule received from a firstneighboring device of the one or more neighboring devices; determining athird multicast wakeup schedule, based at least in part on the secondmulticast wakeup schedule, for use in communicating in the mesh network;and causing to send the third multicast wakeup schedule to the one ormore neighboring devices.

Example 34 is a method comprising: determining that a network statechange has occurred in a mesh network; determining, based at least inpart on the network change, a first multicast wakeup schedule for use incommunicating in the mesh network; determining one or more neighboringdevices in the mesh network to send the first multicast wakeup schedule;and causing to send the first multicast wakeup schedule to the one ormore neighboring devices. In example 35, the method of example 34 canoptionally include the first multicast wakeup schedule being a mastermulticast wakeup schedule. In example 36, the method of any one ofexamples 34-35 can optionally include the first multicast wakeupschedule being a local multicast wakeup schedule. In example 37, themethod of any one of examples 34-36 can optionally include the firstmulticast wakeup schedule being sent to the one or more neighboringdevices in a neighbor awareness network multicast service group (NMSG)message. In example 38, the method of any one of examples 34-37 canoptionally include the first multicast wakeup schedule is sent to theone or more neighboring devices in a neighbor awareness network servicediscovery frame that is sent in a discovery window. In example 39, themethod of any one of examples 34-38 can optionally include the firstmulticast wakeup schedule being sent to the one or more neighboringdevices in a neighbor awareness network schedule update frame. Inexample 40, the method of any one of examples 34-39 can optionallyinclude the mesh network is a neighborhood area network. In example 41,the method of any one of examples 34-40 can optionally include thenetwork state change comprising a user device enrolling in the meshnetwork, a user device leaving the mesh network, network inference inthe mesh network, a power consumption change by a user device in themesh network, or a change in frequency routing topology in the meshnetwork. In example 42, the method of any one of examples 34-41 canoptionally include the first multicast wakeup schedule including aresource allocation for multicast operation. In example 43, the methodof any one of examples 34-42 can optionally include the resourceallocation including a start time. In example 44, the method of any oneof examples 34-44 can optionally include the method further comprising:identifying a second multicast wakeup schedule received from a firstneighboring device of the one or more neighboring devices; determining athird multicast wakeup schedule, based at least in part on the secondmulticast wakeup schedule, for use in communicating in the mesh network;and causing to send the third multicast wakeup schedule to the one ormore neighboring devices.

Example 48 is an apparatus comprising: means for determining that anetwork state change has occurred in a mesh network; means fordetermining, based at least in part on the network change, a firstmulticast wakeup schedule for use in communicating in the mesh network;means for determining one or more neighboring devices in the meshnetwork to send the first multicast wakeup schedule; and means forcausing to send the first multicast wakeup schedule to the one or moreneighboring devices. In example 49, the apparatus of example 48 canoptionally include the first multicast wakeup schedule being a mastermulticast wakeup schedule. In example 50, the apparatus of any one ofexamples 48-49 can optionally include the first multicast wakeupschedule being a local multicast wakeup schedule. In example 51, theapparatus of any one of examples 48-50 can optionally include the firstmulticast wakeup schedule being sent to the one or more neighboringdevices in a neighbor awareness network multicast service group (NMSG)message. In example 52, the apparatus of any one of examples 48-51 canoptionally include the first multicast wakeup schedule being sent to theone or more neighboring devices in a neighbor awareness network servicediscovery frame that is sent in a discovery window. In example 53, theapparatus of any one of examples 48-52 can optionally include the firstmulticast wakeup schedule being sent to the one or more neighboringdevices in a neighbor awareness network schedule update frame. Inexample 54, the apparatus of any one of examples 48-53 can optionallyinclude the mesh network being a neighborhood area network. In example55, the apparatus of any one of examples 48-54 can optionally includethe network state change comprising a user device enrolling in the meshnetwork, a user device leaving the mesh network, network inference inthe mesh network, a power consumption change by a user device in themesh network, or a change in frequency routing topology in the meshnetwork. In example 56, the apparatus of any one of examples 48-55 canoptionally include the first multicast wakeup schedule including aresource allocation for multicast operation. In example 57, theapparatus of any one of examples 48-56 can optionally include theresource allocation including a start time. In example 58, the apparatusof any one of examples 48-57 can optionally include means foridentifying a second multicast wakeup schedule received from a firstneighboring device of the one or more neighboring devices ;means fordetermining a third multicast wakeup schedule, based at least in part onthe second multicast wakeup schedule, for use in communicating in themesh network; and means for causing to send the third multicast wakeupschedule to the one or more neighboring devices.

Example 59 is a method comprising: identifying a multicast wakeupschedule received from a parent device in a mesh network; updating aninternal multicast schedule of a wireless device using the multicastwakeup schedule; determining one or more neighboring devices in the meshnetwork; and causing to send the multicast wakeup schedule to the one ormore neighboring devices. In example 60, the method of example 59 canoptionally include the multicast wakeup schedule being a mastermulticast wakeup schedule.

Example 64 is an apparatus comprising: means for identifying a multicastwakeup schedule received from a parent device in a mesh network; meansfor updating an internal multicast schedule of a wireless device usingthe multicast wakeup schedule; means for determining one or moreneighboring devices in the mesh network; and means for causing to sendthe multicast wakeup schedule to the one or more neighboring devices. Inexample 65, the apparatus of example 64 can optionally include themulticast wakeup schedule being a master multicast wakeup schedule.

Example 66 is a non-transitory computer-readable medium storingcomputer-executable instructions which, when executed by a processor,cause the processor to perform operations comprising: identifying afirst multicast wakeup schedule received from a parent device in a meshnetwork; determining a second multicast wakeup schedule that isdifferent from the first multicast wakeup schedule; determining one ormore neighboring devices in the mesh network; and causing to send thesecond multicast wakeup schedule to the one or more neighboring devices.In example 67, the computer-readable medium of example 66 can optionallyinclude the first multicast wakeup schedule and the second multicastwakeup schedule allowing complimentary use of network resources at thewireless device. In example 68, the computer-readable medium of any oneof examples 66-67 can optionally include the second multicast wakeupschedule being based at least in part on the first wakeup schedule. Inexample 69, the computer-readable medium of any one of examples 66-68can optionally include operations further comprising: determining tosend to the parent device a third multicast wakeup schedule that isdifferent from the first multicast wakeup schedule; determining thethird multicast wakeup schedule based at least in part on the firstmulticast wakeup schedule; causing to send the third multicast wakeupschedule to the parent device; and identifying a fourth multicast wakeupschedule received from the parent device, wherein the second multicastwakeup schedule is based at least in part on the fourth multicast wakeupschedule. In example 70, the computer-readable medium of any one ofexamples 66-69 can optionally include the first multicast schedulecomprising a master multicast wakeup schedule and a local multicastwakeup schedule, and the second multicast wakeup schedule comprises themaster multicast wakeup schedule.

Example 71 is a method comprising: identifying a first multicast wakeupschedule received from a parent device in a mesh network; determining asecond multicast wakeup schedule that is different from the firstmulticast wakeup schedule; determining one or more neighboring devicesin the mesh network; and causing to send the second multicast wakeupschedule to the one or more neighboring devices. In example 72, themethod of example 71 can optionally include the first multicast wakeupschedule and the second multicast wakeup schedule allowing complimentaryuse of network resources at the wireless device. In example 73, themethod of any one of examples 71-72 can optionally include the secondmulticast wakeup schedule being based at least in part on the firstwakeup schedule. In example 74, the method of any one of examples 71-73can optionally include determining to send to the parent device a thirdmulticast wakeup schedule that is different from the first multicastwakeup schedule; determining the third multicast wakeup schedule basedat least in part on the first multicast wakeup schedule; causing to sendthe third multicast wakeup schedule to the parent device; andidentifying a fourth multicast wakeup schedule received from the parentdevice, wherein the second multicast wakeup schedule is based at leastin part on the fourth multicast wakeup schedule. In example 75, themethod of any one of examples 71-74 can optionally include the firstmulticast schedule comprising a master multicast wakeup schedule and alocal multicast wakeup schedule, and the second multicast wakeupschedule comprising the master multicast wakeup schedule.

Example 79 is an apparatus comprising: means for identifying a firstmulticast wakeup schedule received from a parent device in a meshnetwork; means for determining a second multicast wakeup schedule thatis different from the first multicast wakeup schedule; means fordetermining one or more neighboring devices in the mesh network; andmeans for causing to send the second multicast wakeup schedule to theone or more neighboring devices. In example 80, the apparatus of example79 can optionally include the first multicast wakeup schedule and thesecond multicast wakeup schedule allowing complimentary use of networkresources at the wireless device. In example 81, the apparatus of anyone of examples 79-80 can optionally include the second multicast wakeupschedule being based at least in part on the first wakeup schedule. Inexample 82, the apparatus of any one of examples 79-81 can optionallyinclude means for determining to send to the parent device a thirdmulticast wakeup schedule that is different from the first multicastwakeup schedule; means for determining the third multicast wakeupschedule based at least in part on the first multicast wakeup schedule;means for causing to send the third multicast wakeup schedule to theparent device; and means for identifying a fourth multicast wakeupschedule received from the parent device, wherein the second multicastwakeup schedule is based at least in part on the fourth multicast wakeupschedule. In example 83, the apparatus of any one of examples 79-82 canoptionally include the first multicast schedule comprising a mastermulticast wakeup schedule and a local multicast wakeup schedule, and thesecond multicast wakeup schedule comprising the master multicast wakeupschedule.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainimplementations could include, while other implementations do notinclude, certain features, elements, and/or operations. Thus, suchconditional language is not generally intended to imply that features,elements, and/or operations are in any way required for one or moreimplementations or that one or more implementations necessarily includelogic for deciding, with or without user input or prompting, whetherthese features, elements, and/or operations are included or are to beperformed in any particular implementation.

Many modifications and other implementations of the disclosure set forthherein will be apparent having the benefit of the teachings presented inthe foregoing descriptions and the associated drawings. Therefore, it isto be understood that the disclosure is not to be limited to thespecific implementations disclosed and that modifications and otherimplementations are intended to be included within the scope of theappended claims. Although specific terms are employed herein, they areused in a generic and descriptive sense only and not for purposes oflimitation.

What is claimed is:
 1. An apparatus for a neighbor awareness networking(NAN) node in a NAN multicast service group, the apparatus comprisingprocessing circuitry coupled to storage, the processing circuitryconfigured to: receive a NAN multicast service group schedule from a NANmulticast service group originator, wherein the NAN multicast servicegroup schedule is for communicating between a plurality of neighboringNAN devices enrolled in the NAN multicast service group; receive anindication from the NAN multicast service group originator to serve asan enroller of the NAN multicast service group; enroll a firstneighboring NAN device in the NAN multicast service group; and cause toforward the NAN multicast service group schedule to the enrolled firstneighboring NAN device.
 2. The apparatus of claim 1, wherein theprocessing circuitry is further configured to receive an updated NANmulticast service group schedule from the NAN multicast service grouporiginator based on a change.
 3. The apparatus of claim 2, wherein theupdated NAN multicast service group schedule is received in a NANschedule update frame.
 4. The apparatus of claim 2, wherein the updatedNAN multicast service group schedule indicates a time when the pluralityof neighboring NAN devices start to use the updated NAN multicastservice group schedule.
 5. The apparatus of claim 2, wherein theprocessing circuitry is further configured to share the updated schedulewith the modified NAN multicast service group.
 6. The apparatus of claim2, wherein the processing circuitry is further configured to adopt theupdated NAN multicast service group schedule instead of the NANmulticast service group schedule.
 7. The apparatus of claim 1, whereinthe NAN multicast service group schedule comprises one or more resourceallocations.
 8. The apparatus of claim 1, wherein the NAN multicastservice group is a many-to-many NAN group.
 9. A non-transitorycomputer-readable medium storing computer-executable instructions whichwhen executed by one or more processors result in performing operationscomprising:receiving a neighbor awareness networking (NAN) multicastservice group schedule from a NAN multicast service group originator,wherein the NAN multicast service group schedule is for communicatingbetween a plurality of neighboring NAN devices enrolled in a NANmulticast service group; receiving an indication from the NAN multicastservice group originator to serve as an enroller of the NAN multicastservice group; enrolling a first neighboring NAN device in the NANmulticast service group; and causing to forward the NAN multicastservice group schedule to the enrolled first neighboring NAN device. 10.The non-transitory computer-readable medium of claim 9, wherein theoperations further comprise receiving an updated NAN multicast servicegroup schedule from the NAN multicast service group originator based ona change.
 11. The non-transitory computer-readable medium of claim 10,wherein the updated NAN multicast service group schedule is received ina NAN schedule update frame.
 12. The non-transitory computer-readablemedium of claim 10, wherein the updated NAN multicast service groupschedule indicates a time when the plurality of neighboring NAN devicesstart to use the updated NAN multicast service group schedule.
 13. Thenon-transitory computer-readable medium of claim 10, wherein theoperations further comprise share the updated schedule with the modifiedNAN multicast service group.
 14. The non-transitory computer-readablemedium of claim 10, wherein the operations further comprise adopting theupdated NAN multicast service group schedule instead of the NANmulticast service group schedule.
 15. The non-transitorycomputer-readable medium of claim 9, wherein the NAN multicast servicegroup schedule comprises one or more resource allocations.
 16. Thenon-transitory computer-readable medium of claim 9, wherein the NANmulticast service group is a many-to-many NAN group.
 17. A methodcomprising:receiving a neighbor awareness networking (NAN) multicastservice group schedule from a NAN multicast service group originator,wherein the NAN multicast service group schedule is for communicatingbetween a plurality of neighboring NAN devices enrolled in a NANmulticast service group; receiving an indication from the NAN multicastservice group originator to serve as an enroller of the NAN multicastservice group; enrolling a first neighboring NAN device in the NANmulticast service group; and causing to forward the NAN multicastservice group schedule to the enrolled first neighboring NAN device. 18.The method of claim 17, further comprising receiving an updated NANmulticast service group schedule from the NAN multicast service grouporiginator based on a change.
 19. The method of claim 18, wherein theupdated NAN multicast service group schedule is received in a NANschedule update frame.
 20. The method of claim 18, wherein the updatedNAN multicast service group schedule indicates a time when the pluralityof neighboring NAN devices start to use the updated NAN multicastservice group schedule.